Add instructions for configuring ingress in a local cluster (kind/k3d) #152
+181
−34
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request significantly expands and improves the documentation for using ingress in local Kubernetes clusters, specifically covering both
kindandk3denvironments. The changes provide detailed, step-by-step instructions for multiple scenarios, including direct port access, port forwarding, and using different ingress controllers (Contour and Traefik). The documentation now supports a wider range of local setups and offers clearer guidance for accessing deployed services.Expanded local ingress documentation:
kindandk3dclusters, including the use of Contour and Traefik ingress controllers.kind, including example configuration files and usage of the--local-clusterflag./etc/hostsentries) and curl-based access (using Host headers) for bothkindandk3dclusters.k3d-specific improvements:
kindclusters.